Multi-perimeter firewall in the cloud

ABSTRACT

Systems and methods for providing multi-perimeter firewalls via a virtual global network are disclosed. In one embodiment the network system may comprise an egress ingress point in communication with a first access point server, a second access point server in communication with the first access point server, an endpoint device in communication with the second access point server, a first firewall in communication with the first access point server, and a second firewall in communication with the second access point server. The first and second firewalls may prevent traffic from passing through their respective access point servers. The first and second may be in communication with each other and exchange threat information.

This application is a U.S. National Stage application under 35U.S.C. §371 of International Patent Application No. PCT/IB2016/000528, filed,Apr. 7, 2016, which claims the benefit of and priority to U.S.Provisional Application No. 62/144,293 filed on Apr. 7, 2015 and U.S.Provisional Application No. 62/151,174 filed on Apr. 22, 2015, theentire content of each application is incorporated herein by referencein its entirety.

FIELD OF THE DISCLOSURE

The present disclosure relates generally to networks, and moreparticularly, network security which protects the flow of trafficthrough a global virtual network or similar network by the strategicpositioning of distributed firewall (FW) devices placed at multipleperimeters in the cloud.

BACKGROUND OF THE DISCLOSURE

Human beings are able to perceive delays of 200 ms or more as this istypically the average human reaction time to an event. If latency is toohigh, online systems such as thin-clients to cloud-based servers,customer relationship management (CRM), enterprise resource planning(ERP) and other systems will perform poorly and may even ceasefunctioning due to timeouts. High latency combined with high packet losscan make a connection unusable. Even if data gets through, at a certainpoint too much slowness results in a poor user experience (UX) and inthose instances the result can be refusal by users to accept thoseconditions in effect rendering poorly delivered services as useless.

To address some of these issues, various technologies have beendeveloped. One such technology is WAN optimization, typically involvinga hardware (HW) device at the edge of a local area network (LAN) whichbuilds a tunnel to another WAN optimization HW device at the edge ofanother LAN, forming a wide area network (WAN) between them. Thistechnology assumes a stable connection through which the two devicesconnect to each other. A WAN optimizer strives to compress and securethe data flow often resulting in a speed gain. The commercial driver forthe adoption of WAN optimization is to save on the volume of data sentin an effort to reduce the cost of data transmission. Disadvantages ofthis are that it is often point-to-point and can struggle when theconnection between the two devices is not good as there is little to nocontrol over the path of the flow of traffic through the Internetbetween them. To address this, users of WAN optimizers often opt to runtheir WAN over an MPLS or DDN line or other dedicated circuit resultingin an added expense and again usually entailing a rigid, fixedpoint-to-point connection.

Direct links such as MPLS, DDN, Dedicated Circuits or other types offixed point-to-point connection offer quality of connection and Qualityof Service (QoS) guarantees. They are expensive and often take asignificantly long time to install due to the need to physically drawlines from a POP at each side of the connection. The point-to-pointtopology works well when connecting from within one LAN to the resourcesof another LAN via this directly connected WAN. However, when thegateway (GW) to the general Internet is located at the LAN of one end,say at the corporate headquarters, then traffic from the remote LAN of asubsidiary country may be routed to the Internet through the GW. Aslowdown occurs as traffic flows through the internet back to servers inthe same country as the subsidiary. Traffic must then go from the LANthrough the WAN to the LAN where the GW is located and then through theInternet back to a server in the origin country, then back through theinternet to the GW, and then back down the dedicated line to the clientdevice within the LAN. In essence doubling or tripling (or worse) theglobal transit time of what should take a small fraction of globallatency to access this nearby site. To overcome this, alternativeconnectivity of another internet line with appropriate configurationchanges and added devices can offer local traffic to the internet, ateach end of such a system.

Another option for creating WAN links from one LAN to another LANinvolve the building of tunnels such as IPSec or other protocol tunnelsbetween two routers, firewalls, or equivalent edge devices. These areusually encrypted and can offer compression and other logic to try toimprove connectivity. There is little to no control over the routesbetween the two points as they rely on the policy of various middleplayers on the internet who carry their traffic over their network(s)and peer to other carriers and or network operators. Firewalls androuters, switches and other devices from a number of equipment vendorsusually have tunneling options built into their firmware.

While last mile connectivity has vastly improved in recent years therestill exist problems with long distance connectivity and throughput dueto issues related to distance, protocol limitations, peering,interference, and other problems and threats. As such, there exists aneed for secure network optimization services running over the top ofstandard internet connections.

SUMMARY OF THE DISCLOSURE

Systems and methods for providing multi-perimeter firewalls via avirtual global network are disclosed. The network may comprise an egressingress point device, a first and second access point server, anendpoint device, and a first and second firewall. The first firewall isin communication with the first access point server and may preventnetwork traffic from flowing through the first access point server. Thesecond firewall is in communication with the second access point serverand may prevent network traffic from flowing through the second accesspoint server.

In accordance with one embodiment, at least one of the access pointservers is configured to perform firewall services.

In accordance with another embodiment the first firewall is incommunication with the second firewall. The communication path betweenthe first and second firewall may be a global virtual network tunnel ora global virtual network back channel or API call or other. In someembodiments the first firewall and the second firewall share threatinformation including at least one of heuristic patterns, signatures ofknown threats, known malicious source IP addresses, or attack vectors.The threat information may be shared via a central control server.

In some embodiments at least one of the firewalls performs deep packetinspection. In other embodiments at least one of the firewalls performsstateful packet inspection. In other embodiments one firewall performsstateful packet inspection and the other firewall performs statefulpacket inspection.

In some embodiments at least one of the firewalls includes a cloudfirewall load balancer that can allocate cloud firewall resources ondemand.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to facilitate a fuller understanding of the present disclosure,reference is now made to the accompanying drawings, in which likeelements are referenced with like numerals or references. These drawingsshould not be construed as limiting the present disclosure, but areintended to be illustrative only.

FIG. 1 illustrates five types of firewall device operations.

FIG. 2 illustrates traffic flow possibilities through a firewall.

FIG. 3 illustrates stateful packet inspection and deep packetinspection.

FIG. 4 illustrates the generation of a combined payload from a stream ofpackets.

FIG. 5 illustrates a broad based network attack path from the Internetto a LAN.

FIG. 6 shows negative blowback effects on a network due to ahigh-traffic-volume attack occurring on an opposing network.

FIG. 7 illustrates a multi-perimeter firewall located in the cloud.

FIG. 8 illustrates the scalability of a multi-perimeter firewall locatedin the cloud.

FIG. 9 illustrates a multi-perimeter firewall on top of a GVN which ison top of an Internet connection.

FIG. 10 is a flow chart of the various routes available through a GVNfrom an origin to a destination.

FIG. 11 illustrates communication between a stateful packet inspection(SPI) firewall and a deep packet inspection (DPI) firewall.

FIG. 12 illustrates a multi-perimeter firewall (MPFW) in the cloudenabled by a global virtual network.

FIG. 13 illustrates the information flow between devices of a GlobalVirtual Network.

FIG. 14 illustrates a multi-perimeter firewall (MPFW) in the cloudsupporting a personal end point device.

FIG. 15 illustrates the modules required for automated device andfirewall collaboration and information exchange in a GVN.

FIG. 16 illustrates device-to-device exchange of information in a GVN.

FIG. 17 illustrates the integration of a multi-perimeter firewall withother systems in a GVN.

FIG. 18 illustrates the topology and corresponding placement offirewalls along with the scalability afforded by cloud based firewallslinked by cloud based firewall load balancers.

FIG. 19 illustrates GVN topology, including a backbone segment overinternet or dark fiber.

FIG. 20 illustrates the topology of devices and connectivity for theflow of information to and from an end point device (EPD) and theinternet.

FIG. 21 illustrates a multi-perimeter firewall algorithm.

FIG. 22 illustrates a logical view of the software architecture for acloud firewall device, a cloud firewall load balancer device, a centralcontrol server, an access point server, and an end point device.

FIG. 23 illustrates the flow of information from firewalls (FW) tovarious devices in a global virtual network (GVN) via a central controlserver (SRV_CNTRL).

FIG. 24 is a flowchart describing the algorithm used to analyze trafficflowing through a firewall, a firewall load-balancer, and/or through afirewall array.

FIG. 25 illustrates the various layers in a system stack to deal withand handle threats.

FIG. 26 illustrates a method for automatically decrypting an encryptedvolume during a boot-up process.

FIG. 27 illustrates how a unique user identification (UUID) can beconsistently computed for a device based on a number of factors specificto that device.

FIG. 28 illustrates the modules of the secure boot mechanism.

FIG. 29 illustrates the details of the back channel mechanism.

FIG. 30 illustrates the connections between many end point devices (EPD)and a back channel server (SRV_BC).

FIG. 31 illustrates the writing of encrypted data into selected fieldsin a row of a database using rotating and calculated keys which areunique for every single row.

FIG. 32 illustrates the decryption of data from a single row using keys,key adjustors, and other factors using a framework to calculated keys.

FIG. 33 illustrates what happens when graphic user interface (GUI)content which is requested by a client via an end point device (EPD) andthe request content is stored within a locked volume.

FIG. 34 shows a high-level block diagram of the Internet.

FIG. 35 is a block diagram showing the resolution of Universal ResourceLocator (URLs) to numeric Internet Protocol (IP) addresses via theDomain Name System (DNS).

DETAILED DESCRIPTION

A GVN offers secure network optimization services to clients over thetop of their standard internet connection. This is an overview of theconstituent parts of a GVN as well as a description of relatedtechnologies which can serve as GVN elements. GVN elements may operateindependently or within the ecosystem of a GVN such as utilizing the GVNframework for their own purposes, or can be deployed to enhance theperformance and efficiency of a GVN. This overview also describes howother technologies can benefit from a GVN either as a stand-alonedeployment using some or all components of a GVN, or which could berapidly deployed as an independent mechanism on top of an existing GVN,utilizing its benefits.

A software (SW) based virtual private network (VPN) offers privacy via atunnel between a client device and a VPN server. These have an advantageof encryption and in some cases also compression. But here again thereis little to no control over how traffic flows between VPN client andVPN server as well as between the VPN server and host server, hostclient or other devices at destination. These are often point-to-pointconnections that require client software to be installed per deviceusing the VPN and some technical proficiency to maintain the connectionfor each device. If a VPN server egress point is in close proximity viaquality communication path to destination host server or host clientthen performance will be good. If not, then there will be noticeabledrags on performance and dissatisfaction from a usability perspective.It is often a requirement for a VPN user to have to disconnect from oneVPN server and reconnect to another VPN server to have quality or localaccess to content from one region versus the content from anotherregion.

A Global Virtual Network (GVN) is a type of computer network on top ofthe internet providing global secure network optimization servicesutilizing a mesh of devices distributed around the world securely linkedto each other by advanced tunnels, collaborating and communicating viaApplication Program Interface (API), Database (DB) replication, andother methods. Traffic routing in the GVN is always via bestcommunication path governed by Advanced Smart Routing (ASR) powered byautomated systems which combine builders, managers, testers, algorithmicanalysis and other methodologies to adapt to changing conditions andlearning over time to configure and reconfigure the system.

The GVN offers a service to provide secure, reliable, fast, stable,precise and focused concurrent connectivity over the top of one or moreregular Internet connections. These benefits are achieved throughcompression of data flow transiting multiple connections of wrapped,disguised and encrypted tunnels between the EPD and access point servers(SRV_AP) in close proximity to the EPD. The quality of connectionbetween EPD and SRV_AP's is constantly being monitored.

A GVN is a combination of a hardware (HW) End Point Device (EPD) withinstalled software (SW), databases (DB) and other automated modules ofthe GVN system such as Neutral Application Programming InterfaceMechanism (NAPIM), back channel manager, tunnel manager, and morefeatures which connect the EPD to distributed infrastructure devicessuch as access point server (SRV_AP) and central server (SRV_CNTRL)within the GVN.

Algorithms continually analyze current network state while taking intoaccount trailing trends plus long term historical performance todetermine best route for traffic to take and which is the best SRV_AP orseries of SRV_AP servers to push traffic through. Configuration,communication path and other changes are made automatically and on thefly with minimal or no user interaction or intervention required.

Advanced Smart Routing in an EPD and in an SRV_AP ensure that trafficflows via the most ideal path from origin to destination through an assimple as possible “Third Layer” of the GVN. This third layer is seen byclient devices connected to the GVN as a normal internet path but with alower number of hops, better security and in most cases lower latencythan traffic flowing through the regular internet to the samedestination. Logic and automation operate at the “second layer” of theGVN where the software of the GVN automatically monitors and controlsthe underlying routing and construct of virtual interfaces (VIF),multiple tunnels and binding of communication paths. The third andsecond layers of the GVN exist on top of the operational “first layer”of the GVN which interacts with the devices of the underlying Internetnetwork.

The cloud from a technical and networking perspective refers to devicesor groups or arrays or clusters of devices which are connected and areavailable to other devices through the open internet. The physicallocation of these devices is not of significant importance as they oftenhave their data replicated across multiple locations with deliveryto/from closest server to/from requesting client utilizing contentdelivery network (CDN) or other such technology to speed connectivitywhich enhances user experience (UX).

This invention builds upon the standard use by industry of firewalls(FW) increasing their utility value by extending perimeters into thecloud. A firewall is a device primarily designed to protect an internalnetwork against the external threats from an outside network, as well asprotecting the leakage of information data from the internal network. Afirewall has traditionally been placed at the edge between one networksuch as a local area network (LAN) and another network such as itsuplink to a broader network. Network administrators have sensitivitiesabout the placement and trustworthiness of a FW because of theirreliance on it to secure their networks.

Additional components of the GVN include the secure boot mechanism (SBM)and the back channel mechanism (BCM). The secure boot mechanism protectsthe keys of a secure volume by storing the key on a remote server andonly making the key available via the SBM. The back channel mechanismallows for the administration and/or interaction of many devices of aGVN. During times of poor network performance when a tunnel goes down,the BCM offers a channel into devices which cannot otherwise be reached,including access to devices which are not reachable from the openinternet. This mechanism offers reverse hole-punching through barriersto keep the communications channel open. Other security components ofthe GVN include UUID hardware binding and fine granularity dataencryption using per row keys.

FIG. 34 shows a high-level block diagram of the Internet. The averageuser possesses a very cursory overview understanding of how the Internetfunctions. Host Source 34-100 is the starting point and denotes a clientdevice which could be a computer, a mobile phone, tablet, laptopcomputer or other such client. This client connects via the Internet34-200 to a host server 34-300 to send or retrieve content, or toanother host client 34-302 to send or receive information.

A very non-technical user might assume that traffic to the host serverfollows path 2P002 without even understanding that their data willtransit through the Internet. Or they might think that traffic wouldflow via path 2P006 directly to another client device.

A user with some more understanding of how it works would understandthat traffic flows via path 2P004 to the Internet 34-200 and then viapath 2P102 to a Host server Target 34-300 or via path 2P104 to a Host(client) Target 34-302.

Users with some more technical knowledge will further understand thatwhen sending an email, the this email will leave their client device34-100, transit via path 2P004 to the Internet 34-200 and then via path2P202 to a mail server 34-202. Then the recipient of the email will makea request to retrieve the email via their host client 34-302 along path2P104 to the Internet and then down path 2P204 to the mail server34-202.

This is about as detailed as the average person's understanding of theInternet gets.

FIG. 35 is a block diagram showing the resolution of Universal ResourceLocator (URLs) to numeric Internet Protocol (IP) addresses via theDomain Name System (DNS).

A content request 35-000 or push from host client (C) 35-100 to hostserver (S) 35-300 as files or streams or blocks of data flows from hostclient (C) 35-100 to the host server (S) 35-300. The response or contentdelivery 35-002 is returned from host S to host C as files or streams orblocks of data. The host client device 35-100 in a Client-Server (CS)relationship with host server (S) makes requests to access content fromthe remote host server (S) or sends data to remote host server (S) via auniversal resource locator (URL) or other network reachable address.

The initial connection from the host client (C) 35-100 to the Internet35-206 is shown as 3P02—the connection from the host client (C) to aPoint of Presence (POP) 35-102 that can be directly facing. In othercases the host client (C) can be located in a local area network (LAN)which then connects to the internet via a point of presence (POP) andcan be referred to as the last mile connection. The point of presence(POP) 35-102 represents the connection provided from an end point by aninternet service provider (ISP) to the internet via their network andits interconnects. This can be, but is not limited to, cable, fiber,DSL, Ethernet, satellite, dial-up, and other connections. If the URL isa domain name rather than a numeric address, then this URL is sent todomain name system (DNS) server 35-104 where the domain name istranslated to an IPv4 or IPv6 or other address for routing purposes.

Traffic from host client (C) 35-100 to host server (S) 35-300 is routedthrough the Internet 35-206 representing transit between POPs (35-102and 35-302) including peering, backhaul, or other transit of networkboundaries.

The connection 3P04 between a POP 35-102 and a domain name system35-104, used to look up a number address from a universal resourcelocator (URL) to get the IPv4 address or other numeric address of targetserver (S), can be directly accessed from the POP, or via the Internet35-206. The connection 3P06 from a POP 35-102 of an ISP to the Internet35-206 can be single-homed or multi-honed. Similarly, the connection3P08 from the Internet 35-206 to the remote ISP can also be single-homedor multi-honed. This connection is generally, to the ISP's or InternetData Center's (IDC) internet-facing POP 35-302. The connection 3P10 fromthe remote ISP's POP 35-302 to the host server (S) can be direct or viamultiple hops.

The lookups from URL or hostname to numeric address via domain namesystems is a standard on the Internet today and systems assume that theDNS server is integral and that the DNS server results are current andcan be trusted.

FIG. 19 illustrates GVN topology, communications paths including abackbone segment over internet or dark fiber and indicates the placementof various devices including various types of firewall (FW) devices atvarious perimeter locations. It shows how various geographic regions orzones or territory are linked together over various types of paths. Thisfigure illustrates that various types of network fabrics can be combinedinto a greater network tapestry. These fabrics can be seamlessly woventogether as described in U.S. Provisional Patent Application No.62/174,394.

Referring to FIG. 19, there are multiple zone shown: LAN zone 0 (ZL00),LAN zone 1 (ZL10), Internet zone 0 (ZI00), Internet zone 1 (ZI10),Internet zone 2 (ZI20), Internet zone 3 (ZI30), Internet data centerzone 2 (ZD20), and Internet data center zone 3 (ZD30).

LAN zone 0 19-ZL00 describes a typical local area network (LAN)including the placement of firewalls with respect to an end point device(EPD) 19-100 between the LAN and the external network GVN OTT 19-202 andInternet 19-30. There is a hardware firewall FW 19-40 between LAN 19-04and EPD 19-100. Another hardware or software FW 19-42 is between the EPD19-100 and the egress ingress point (EIP) 19-20 to protect the EPD fromexternal threats emanating from Internet 19-30.

LAN zone one 19-ZL10 is similar in topology to LAN zone zero 19-ZL00with the exception that there is no firewall placed between EPD 19-110and LAN 19-46.

Internet zone zero 19-ZI00 describes an example internet topology in aregion in close proximity to 19-ZL00. Internet zone one 19-ZI10describes an example internet topology in a region in close proximity to19-ZL10. Internet zone two 19-ZI20 describes an example internettopology in a region in close proximity to 19-ZD20. Internet zone three19-ZI30 describes an example internet topology in a region in closeproximity to 19-ZD30.

Internet data center zone two 19-ZD20 describes the topology andplacement of cloud based firewalls CFW 19-46 including virtualizedfirewall devices behind cloud firewall load balancers. Internet datacenter zone three 19-ZD30 describes the topology and placement of cloudbased firewalls CFW 19-48 including virtualized firewall devices behindcloud firewall load balancers.

SRV_BBX 19-72 in region or zone ZD20 can be connected to SRV_BBX 19-80in another region or zone ZD30 via a dark fiber connection 19-P220 overdark fiber 19-220. SRV_BBX 19-72 can directly write a file to parallelfile storage PFS 19-82 via remote direct memory access (RDMA) over19-P220 bypassing the stack of SRV_BBX 19-80 via path 19-P82. SRV_BBX19-80 can directly write a file to parallel file storage PFS 19-74 viaremote direct memory access (RDMA) over 19-P220 bypassing the stack ofSRV_BBX 19-72 via path 19-P74.

Path 19-P210 can be IPv4 or some kind of standardized internet protocolover which traffic flows from SRV_AP 19-300 to and or from SRV_AP 19-310via path 19-P210 over-the-top of the GVN via a tunnel or other type ofcommunication path.

While the topology shown does not have firewalls or traffic monitoringdevices within the GVN pathways, these devices could be placed there onan as needed basis to further secure the flow of data.

FIG. 13 illustrates the information flow between devices of a GlobalVirtual Network. A central repository comprised of database B200 andfile storage HFS200 resides on a Central Server (SRV_CNTRL) 200.

Communication paths between devices labeled P### can represent an APIcall, database replication, direct file transfer, combination such asdatabase replication through API call, or other form of informationexchange. The thicker lines of 13-P100300, 13-P300500, and 13-P100500represent direct communications between GVN devices which have apeer-pairing and therefore a privileged relationship with each other.

There is circular pattern of peer-pair communication illustrated fromSRV_CNTRL 200 to EPD 100 via 13-P200100, to SRV_AP 300 via 13-P200300,or to other devices 13-500 via 13-P200500. The EPD 100 communicates withSRV_CNTRL 200 via 13-P100200, SRV_AP 300 communicates via SRV_CNTRL 200via 13-P300200, and other devices 13-500 communicate with SRV_CNTRL 200via 13-P500200.

In some instances, there will be a loop of information shared betweendevices such as in the case when an EPD 100 may request information via13-P100200 from SRV_CNTRL 200 which is sent back to EPD 100 via13-P200100.

In other instances, one device may report information relevant to otherdevices such as an SRV_AP 200 reporting via 13-P300200 to SRV_CNTRL 200which it then sends this information via 13-P200100 to EPD 100 andSRV_AP 300 other than the reporting SRV_AP 300 via 13-P200300 and alsoto other devices 13-500 via 13-P200500.

In yet other instances a full loop is not required such as the sendingof log information from a device such as an EPD 100 to SRV_CNTRL 200 via13-P100200, there is no need to further forward this information onward.However, logging information may at a later time be moved fromrepository on SRV_CNTRL 200 to a long-term log storage server 13-500 oranother device via 13-P200500.

Direct link 13-P100300 is between devices EPD 100 and SRV_AP 300. Directlink 13-P300500 is from SRV_AP 300 to other devices 13-500. Direct linksinvolve communications between devices which do not need involvement ofSRV_CNTRL 200.

The Push (feed) from SRV_CNTRL 13-306 from SRV_CNTRL 200 could be an RSSfeed or other type of information publishing via 13-P306. TheAPI—Queries to SRV_CNTRL 13-302 making calls to SRV_CNTRL 200 could beeither a traditional API transaction or RESTful API call with requestmade via 13-P302REQ and response received via 13-P302RESP. The PUSH13-306 and API 13-302 elements are presented to illustrate communicationwith devices which do not share peer-pair relationships, privilegedstatus, and/or similar systems architecture with GVN devices but whichcould benefit from information.

FIG. 1 illustrates five types of firewall device operations. Firewall1-FW0 demonstrates an all-open firewall with some closures shown. Path1-DP0-2 indicates a flow of traffic which is permitted through thefirewall because it is not explicitly blocked. Path 1-DP0-4 demonstratestraffic which is not let through the firewall because it is explicitlyblocked.

Firewall 1-FW2 demonstrates an all-closed firewall with some openingsshown. Path 1-DP2-4 indicates traffic which is not explicitly allowed topass through by a rule and therefore is blocked. Path 1-DP2-2 indicatestraffic which is explicitly allowed and therefore flows throughunimpeded.

Firewall 1-FW4 demonstrates a rules-based firewall with two rules shown.Incoming traffic flows from the Internet 1-D104 via path Incoming 1-DP4to a table of rules 1-D4 for forwarding or other handling. If theincoming traffic matches one rule, it will flow via path Rule 1-DP4A toLAN 1-D104. If it matches another rule, it will flow via path Rule1-DP4B to another location in LAN 1-D104.

Firewall 1-FW6 demonstrates firewall operations such as detect & protectwith a decision matrix 1-D6 to check if traffic is okay and should bepermitted through via path YES 1-DP6Y to LAN 1-D106 or if a threat isdetected and the traffic is to be blocked and/or blackholed or otherwisehandled via path NO 1-DP6N.

Firewall 1-FW8 demonstrates a firewall with a combination of rules plusdetect & protect operations 1-D8 shown. Traffic from Internet 1-D108 caneither match rules and flow via rule path Rule 1-DP8A or Rule 1-DP8B ofLAN 1-D108, or it can be allowed by a direct & protect filter via pathYES 1-DP8Y. If the traffic is not allowed, it will be blocked orblackholed or otherwise handled via path NO 1-DP8N.

Another type of firewall not shown is a combination of Firewall 1-FW0 orFirewall 1-FW2 and Firewall 1-FW8. There are also different kinds ofdetect and protect firewalls not shown such as Stateful packetinspection (SPI), deep packet inspection (DPI) and other types offirewalls.

FIG. 2 illustrates traffic flow possibilities through a firewall. Theconnectivity path between the last mile POP 2-022 and LAN 2-114 is via2-CP144 from POP to FW 2-144 and via 2-CP114 from LAN 2-114 to FW 2-144.Bad, offending, or known threat traffic to be caught can either be sentto blackhole 2-148 via path 2-TR6A to 2-TR6B or data quarantined inFW-Quarantine 2-144Q via path 2-TR4A to 2-TR4B. Path for good,unchallenged or allowed traffic can flow via 2-TR2. External to internalattack traffic is represented by 2-ATK-434 and 2-ATK-432.

FIG. 3 illustrates two kinds of inspection that a firewall can perform:stateful packet inspection and deep packet inspection. In the case wherea firewall is within one physical device there exists a choice ofwhether to do SPI or DPI, as a trade-off of speed versuscomprehensiveness. Stateful packet inspection (SPI) is shown in SPIFirewall 3-SP and deep packet inspection (DPI) is shown in DPI Firewall3-DP.

When performing SPI the firewall examines the headers 3-SP0-H, 3-SP2-H,and 3-SP4-H of packets to identify offending information while itignores the payload 3-SP0-P, 3-SP2-P, and 3-SP4-P of the packets. Theadvantages of SPI over DPI are that it is fast and that it consumeslower processor, RAM and resources. The disadvantage is that thefirewall does not look at the content within the payload of thepacket(s).

DPI looks beyond headers 3-DP0-H, 3-DP2-H, 3-DP4-H, 3-DP6-H, and 3-DP8-Hand examines the content, e.g. payload 3-DP0-P, 3-DP2-P, 3-DP4-P,3-DP6-P, and 3-DP8-P of the packets. The advantages are that thisexamination is more comprehensive in providing visibility into contentboth within the payload of not just one packet but from a compilationpayload 3-DP-ALL from a series of multiple packets 3-DP0, 3-DP2,3-DP4-H, 3-DP6, and 3-DP8. The disadvantage of DPI is that it issignificantly slower than SPI and also that it consumes considerablymore processor, RAM, and other resources than SPI.

FIG. 4 illustrates the generation of a combined payload from a stream ofpackets. In this example, a stream of packets 4-DP is presented to a DPIfirewall. The payloads 3-DP0-P6, 3-DP2-P6, 3-DP4-P6, 3-DP6-P6, and3-DP8-P are joined into the combined payload 3-DP-ALL which is thenanalyzed by DPI Firewall 4-DP-ANL.

Deep packet inspection operates by examining the payload of one or morepackets. It looks closely at the contents of the payload and can besearching for: a search string, a known virus signature or a heuristicsignature indicative of a virus, malware patterns, malformed binaryblobs masquerading as a different data types, or other threats, known orunknown.

FIG. 5 illustrates a broad based network attack path from the Internet002 to a LAN 114. This figure shows the relative pipe size or bandwidthof each network segment. An internal LAN NTSP08 may be running at aspeed of 10 GigE. This network segment includes the connection CP114between the ISP's POP 022 and the internal firewall FW 144. The localISP's network NTSP04 may also be 10 GigE. This network segment includesthe connection CP022 between the Internet and the ISP's POP 022. Thespeed of the Internet backbone network NTSP02 will generally besignificantly faster, such as a multi-honed 3*100 GigE network.

However, the “last mile” connection network NTSP06 between the clientfirewall FW 144 and POP 022 of the ISP will generally be much slower.For example the connection CP 144 between FW 144 and POP 022 may be a200 Mbps connection, rather than the faster 10 GigE speed of eitherNTSP04 or NTSP08. Because this connection has less bandwidth, e.g. isslower, this connection can easily be saturated by a coordinatedinternet-based attack. The ISP's POP 022 can become saturated as well,affecting not just this client's connectivity but others' as well.

FIG. 6 shows negative blowback effects on a network due to ahigh-traffic-volume attack occurring on an apposing network. When pathCP144 is oversaturated with attack traffic ATK-432 and ATK-434, this mayhave a negative effect on apposing networks paths CP142 (connecting tofirewall FW142 and path CP112 to LAN 1120) and CP146 (connecting tofirewall FW146 and path CP116 to LAN 116). This is due to the closeproximity of CP142 and CP146 with CP144 and their shared up-stream pathsthrough POP 022.

The negative effects on CP142 and CP146 could be due to congestion ofports on shared switches with CP144 as well as other factors. Inaddition, congestion issues in the pipe CP022 from the Internet to thePOP 022 affects all traffic between the ISP's POP 022 and the Internet002. Congestion issues POP 022 also can affect flow of traffic throughthe POP and saturate ISP bandwidth, thereby negatively impacting devicetraffic throughput.

Although CP142 and CP146 may not be directly attacked, they will stillbe adversely affected by attacks on CP144 through the common POP 022 andpath CP022.

FIG. 7 illustrates a multi-perimeter firewall located in the cloud.Locating a multi-perimeter firewall in the cloud has the advantage ofidentifying and isolating problem traffic at a point upstream from thelocation of a traditional firewall. By deploying a multi-perimeterfirewall in the cloud CFW 7-144LB, problem traffic is identified andisolated on the ISP's backbone network 7-NTSP02. The problem traffic isdiverted and does not reach the “last mile” connection network 7-NTSP06.This means that the slow 200 Mbps “last mile” connection network7-NTSP06 is insulated and protected from the high volume of traffic frommultiple concurrent attack vectors present on the faster 3×100 GigEbackbone network 7-NTSP02.

FIG. 8 illustrates the scalability of a multi-perimeter firewall locatedin the cloud and demonstrates how a feature like a distributed firewall(FW) in the cloud can be enabled by a GVN. Cloud based firewalls aredynamically scalable via cloud firewall load balancing mechanisms thatcan bring more resources online as needed. Because of the nature of aGVN's topology, device-to-device communications, and secure trafficpath, a firewall mechanism can be cloud based and also can bevirtualized. Firewall 8-144 is located in cloud between the Internet8-000 and GVN 8-028. Firewall 8-144 can include a cloud firewall (CFW)load balancer 8-144LB which will be able to allocate cloud firewallresources such as 8-144-2, 8-144-3, and so on as needed. This on demandscalability offers many advantages to clients of a GVN.

First, by absorbing the hits of the attacks for incoming threats in thecloud, the client's last mile connectivity is not affected. Second,combining a cloud firewall with a control node and analyzer allows forthe firewall in the region under attack to be aware of the nature,source, signature and other features of the attack so that the firewallcan be aware of and be prepared to thwart the attack if the targetshifts to a different client network. Furthermore, information aboutpast and current attacks can be shared via the neutral API mechanism(NAPIM) of the GVN to other CFW instances, so that global threatawareness is possible.

Finally, as shown below in FIG. 12, a cloud firewall offers theadvantage of running different firewall mechanisms, such as SPI and DPI,simultaneously.

FIG. 9 illustrates a multi-perimeter firewall over the top (OTT) of aGVN which is itself over the top (OTT) of an Internet connection. Thisfigure demonstrates layered functionality built over the top (OTT) ofother layered functionality. For example, a multi-perimeter firewall(MPFWM) 9-88 which is OTT² 9-TOP88 of a global virtual network (GVN)9-86. The GVN 9-86 is OTT¹ 9-TOP86 of the Base Internet Connectivity9-82 at the layer ISP network service link to Internet 9-TOP82.

OTT² is second degree over-the-top meaning that something isover-the-top of something which is itself OTT¹ over-the-top of somethingelse.

FIG. 10 is a flow chart of the various routes available through a GVNfrom an origin C 10-002 to destination S 10-502. There can be many morepossible combinations that are not shown or discussed.

Path 10-CP00 from the Client C 10-002 to the EPD 10-108 can be used tomeasure the performance from the client through the LAN to the EPD.Matching of best routes is achieved after tests and evaluating real-timedata of available paths. GVN ingress is from EPD 10-108 via first hop10-CP00 to an access point server (SRV_AP) 10-102, 10-104, 10-106,10-202, 10-204. Paths from EPD 10-108 to a first SRV_AP can be definedas the ingress point from the EPD 10-108 into the GVN and measuredaccordingly. Internal hops from SRV_AP to SRV_AP follow internal routeswhich always try to maintain the best path connectivity. These routescould be OTT internet, over backbone, over dark fiber, or other relatedrouting. Best egress points out of the GVN are also kept track oflocally, in that remote region and also holistically for the entirenetwork segment from origin to destination.

Tests can be run on each segment, combinations of segments, and thetotal network path from end to end taking into account various factorsto evaluate. Traffic type and path determination can be depending ondata attributes and profile QoS requirements. The main path choice isalways based on best factors for traffic over path. A function of thismechanism is to match paths between destination and origin to flow forbest possible bidirectional route.

The heart of advanced smart routing (ASR) within a GVN is an indexstored on disk, in memory, or in a database table. The index contains alist of IP addresses to keep local and will exit via an EIP in the sameregion. For traffic through a GVN to other regions, routes via SRV_APdevices and paths are determined by Server Availability Matrix (SAM) andASR. The index stores a list of targets matching target IP address tobest egress/ingress points (EIP) in that region. In addition a table ofcountry IP addresses mapped to regions as CIDR IP blocks or other typeof notation can assist in the determination of best egress points.

For traffic flowing in the direction of Origin C 10-002 from Dest. S10-502, the first EIP 10-320, 10-322, 10-334, 10-326, or 10-328 is theinitial boundary between the GVN and the Internet, other networks (suchas LANs), backbone pipes, or others. An SPI firewall can be located inthe GVN behind this initial entry point demarking the first, outerperimeter. At the next SRV_APs or at other SRV_APs such as SRV_AP10-102, 10-104, 10-204, and 10-206, a second perimeter of trailing DPIfirewalls can be located. The client can also run an inbound SPI or DPIfirewall in their own network if they want at segment 10-CP00.

For traffic flowing in the direction of Dest. S 10-502 from Origin C10-002 though EPD 10-108, the first SPI/DPI firewalls can be locatedbetween the Origin C 10-002 and EPD 10-108 along path 10-CP00. A secondperimeter of firewalls can be located on SRV_APs such as 10-102, 10-104,10-204, and 10-106 to protect outbound traffic.

For traffic from the internet, cloud scalability is very importantbecause it can handle the peak load of a distributed, multi-honedtraffic when needed by scaling up resources allocation. When activity isrelatively quiet, a minimal amount of resources can be committed. Thescalability of resources is not as critical of a factor for outboundtraffic to the internet. In most cases, the LAN network will havegreater bandwidth than the network uplink. Scalability is less criticaldue to the nature of threats from within a LAN/DMZ/network under controlof the network administrator(s).

FIG. 18 illustrates the topology and corresponding placement offirewalls along with the scalability afforded by cloud based firewallslinked by cloud based firewall load balancers. This figure is similar toFIG. 10 with the additional placement of various SPI and DPI cloud-basedfirewalls within the flow of traffic via a series of paths through a GVNor other type of network paths.

Stateful packet inspection firewalls (SPI) are devices through which thetraffic flows. Deep packet inspection firewall (DPI) devices can eitherbe flow through or can analyze cloned copies of traffic offering theoption for DPI functionality as a trailing indicator. If harmful trafficis detected, it can subsequently blocked once identified. A benefit ofthe communication between devices is that information about bad trafficsources identified by DPI firewalls can be messaged to SPI firewalls tobe blocked there.

FIG. 11 illustrates communication between a stateful packet inspection(SPI) firewall and a deep packet inspection (DPI) firewall. This figureshows the path from an end point device (EPD) 11-100 to the Internet11-002 via the path TUN 11-0 to a first access point server (SRV_AP)11-302 then to a cloud firewall load balancer (CFW_LB) device 11-144LBvia TUN 11-4, and then to SRV_AP 11-304 via TUN 11-6. From SRV_AP 11-304traffic egresses the GVN via egress ingress point (EIP) 11-E2 to theinternet 11-002.

EIP 11-E2 is the edge of the extended LAN into the cloud between the GVNand the internet 11-002. The EIP can link to both the open internet orto an organization's cloud-based assets including servers, storagearrays, and other devices. It can also be a link to a hybridpublic-private cloud acting like a DMZ or perimeter network in thecloud.

Traffic through SRV_AP 11-302 can be a diversion of traffic or as clonedtraffic in a duplicate stream and passed via path TUN 11-2 to cloud loadbalancer 11-142LB. A cloned stream of traffic offers trailing results oftime- and resources-expensive detection operations such as DPI withoutimpeding the speed of the flow of traffic. Return traffic from Internet11-002 back to EPD 11-100 follows the reverse path ingressing into theGVN via EIP 11-E2.

For internet-based traffic, the first perimeter is the CFW 11-144LBwhich sends packets via the paths 11-CPSP0 and 11-CPSP2 to the Statefulpacket inspection firewall FW (SPI) 11-SP0-PRO where the headers of thepacket 11-SP0-H are inspected. SPI firewalls offer fast trafficflow-through and demand relatively lower resources than DPI firewalls.

The second perimeter is at CFW 11-142LB and this is where the deeppacket inspection firewall FW (DPI) 11-DP0-PRO can inspect the payloads11-DP0-P of one or more combined packets. DPI firewalls offer morein-depth analysis. If payload shows a problem, then the source, target,and other information from the headers can be noted.

Communication between SPI firewalls and DPI firewalls can therefore beuseful. The FW (SPI) 11-SP0-PRO may send information from real-timedetections via path 11-APFW-SP to the cloud firewall load balancer CFW11-142LB to alert it to any threats that it has detected by headerinspection. In addition to sharing the offending headers detected, thepayloads 11-SP0-P will also be included when conveying information toCFW 11-142LB and 11-DP0-PRO. The FW (DPI) 11-DP0-PRO may sendinformation via path 11-APFW-DP to the cloud firewall load balancerCFW-11144LB to alert it to any threats that it has detected by payloadinspection. The information it shares can also be from header 11-DP0-Hso that the SPI firewall detection operations by 11-144LB and/or11-SP0-PRO can add the offending headers to its list of trafficoffenders.

FIG. 12 illustrates a multi-perimeter firewall (MPFW) in the cloudenabled by a global virtual network (GVN). The GVN tunnel 12-TUN0 isover the top (OTT) of the internet between an end point device (EPD)12-100 and an access point server (SRV_AP) 12-300 in close proximity tothe EPD 12-100.

The three perimeters indicated in this example embodiment are 12-M1which denotes the boundary between a client location and their link tothe internet, 12-M2 which is a boundary in the cloud at a datacenter inclose proximity to SRV_AP 12-300, and 12-M3 which is another boundary ateither the same data center as SRV_AP 12-300 or at another location inclose proximity to SRV_AP 12-302, possibly in another region.

The tunnel 12-TUN2 is similar to 12-TUN0 and different in one respect inthat it connects a personal end point device (PEPD) 12-130 which can bemobile and therefore connects to SRV_AP 12-300 through public accesswireless or wired or other networks to integrate into the GVN. A PEPD12-130 may be less powerful than an EPD 12-100 and consequently shiftprocessing operations to the SRV_AP as shown in FIG. 14 below.

Each SRV_AP 12-300 and SRV_AP 12-302 may represent one or more SRV_APdevices through which the EPD 12-100 and/or EPD 12-130 may concurrentlyconnect with via one or more multiple tunnels.

There are three types of firewall described in this example embodiment.Local firewall FW local 12-442 is an example of a firewall which aclient may use to protect their local area network (LAN) from internetbased threats. This is typically located between the EPD 12-100 and theLAN 12-000. Local firewall FW local 12-442 may offer features such as IPaddress and port blocking, forwarding, and other functionality. Theother two types of firewall illustrated are FW SPI 12-446 located at12-M3 which provide stateful packet inspection (SPI) and FW DPI 12-444located at 12-M2 which provides deep packet inspection (DPI).

The difference between SPI and DPI has to do with a tradeoff inperformance versus comprehensiveness of visibility. SPI examines theheaders of packets to look for malformed information, or for patterns,or to match IP address or port or other information from its list ofknown threats against the current flow of packets. DPI as its nameimplies takes a deeper look at the whole packet and in the case of amulti-part, multi-packet transmission, will look at the compilation of aseries of a packets to gain insight into the data being transferred.

All firewalls can be configured to investigate and apply rules to bothincoming and outgoing traffic, and provide other related functionality.In many cases, with traditional firewall such as FW 12-442,administrators have to choose between the efficiency of SPI vs. thethoroughness yet resource and time intensive requirements of DPI.

A GVN offers the opportunity to distribute both types of packetinspection at various points in the cloud. In addition the GVN allowsfor the distributed firewalls to be operating in lockstep with eachother, without impeding the flow of traffic.

By locating FW SPI 12-446 at 12-M3, the closest edge to the Internet12-302 via EIP remote 12-310, the bulk amount of attack traffic fromknown source IP addresses or with recognized malicious headers can bethwarted. Traffic flows from SRV_AP 12-302 to FW SPI 12-446 via 12-T10and back via 12-T12. FW SPI 12-446 can be a CFW load balancer (see FIG.11) which has plenty of resources available on demand. SRV_AP's at 12-M3can be on a multi-honed backbone with a large bandwidth (BW) capacity.Therefore, at this first perimeter, attacks can be caught, protectingbandwidth within the GVN.

At the next perimeter 12-M2, the FW DPI 12-444 can have all traffic flowthrough or just receive a cloned copy of traffic via 12-T20 from SRV_AP12-300 and it may or may not return traffic via 12-T22. The key point isthat the DPI feature can be a trailing indicator allowing certaintraffic through but analyzing and recording the results. This FW DPI12-444 can also be a CFW which is load balanced with resources availableon demand as needed to cope with large scale events when needed withoutindividual clients having to administer or bear the cost burden formaintaining the infrastructure during normal times.

The information from FW SPI 12-446 and FW DPI 12-444 can be shared viainternal communications path 12-P6 which may be carried by the NAPIM ofthe GVN, through a GVN tunnel, through a GVN back channel, or via othercommunications pathway(s). Each FW mechanism also shares informationwith the central control servers (SRV_CNTRL) 12-200 of the GVN. Thisinformation can be relayed to other FW SPI and FW DPI around the worldso that attack vectors, sources, payloads, and other related informationcan be made available in a database or other information index so thatSPI and DPI FW can have a point of reference to check against. Thispermits more efficiencies of scale as the global distribution of infoprovides an added safety net.

The catching of offending traffic outside of a client LAN and in thecloud protects the client's last mile internet connectivity from beingsaturated by unwanted traffic. Offloading of traffic to CFW which arescalable also offers many advantages to clients.

The FW local 12-442 may be a standalone device, a software application(APP) running inside of the EPD 12-100, or other kind of FW device. TheFW SPI 12-446 and FW DPI 12-444 devices and related devices such as loadbalancers, cloud firewalls, or other devices may be custom made or canbe off the shelf provided by other vendors. These devices must be ableto receive and forward traffic, identify threats and most importantly tobe able to communicate their threat findings and to receive threatprofiles and other information from other devices.

As the threat data accumulates, analysis can be made of the content, thepatterns, the attack vectors, and other information gathered by the FWs.This analysis can provide a basis through which heuristic analysis canbe applied to new potential threats.

This can only be achieved by the secure network optimization (SNO)services of a GVN or similar network which consists of related devicesconnected both by secure tunnels and communication paths.

FIG. 14 illustrates a multi-perimeter firewall (MPFW) in the cloudsupporting a personal end point device. This figure is similar to FIG.12 but shows portable devices which would hook into the GVN from amobile location and where 14-M1 boundary is the edge between a personalarea network PAN 14-010 and the GVN.

This figure shows the topology of a personal end point device (PEPD)14-130 with some of its connectivity and other functionality distributedin the cloud. This figure further describes firewall operationsdistributed into the cloud along with those other operations performedin the cloud on behalf of a local device such as a personal end pointdevice (PEPD) 14-130. Where a PEDP 14-130 is a less powerful and moreportable device than an end point device (EPD), it can still takeadvantage of the personal area network connectivity optimizationafforded by a GVN, including features such as advanced smart routing(ASR), multi-perimeter firewalls, and more.

The key point illustrated is that the personal device spreads its needfor processing power into the cloud. The modules residing on the PEPDinclude hardware components for processor CPU 106, memory RAM 108, andnetwork interface NIC 102. The operating system is a minimal O/S 110 toprovide a platform for system software System SW 112 and a Connectivity172 module. This basic configuration is enough to allow the PEPD 14-130to build a tunnel 14-TUN2 between itself and an access point serverSRV_AP 14-300.

The component parts at the SRV_AP 14-300 hardware components forprocessor CPU 306, memory RAM 308, and network interface NIC 302. Theoperating system O/S 310 is a more extensive install than O/S 110. O/S310 provides a platform for system software System SW 312 and aConnectivity 372 module for the SRV_AP 14-300. Advanced smart routing(ASR) 350 module and other modules 370 offer functionality both to theSRV_AP 14-300 and to the connected PEPD-14-130.

The PEPD 14-130 may be dependent on the tunnel 14-TUN2 to be up and ableto carry traffic to realize cloud based ASR, FW and other operationalfunctionality.

FIG. 15 illustrates the modules required for automated device andfirewall collaboration and information exchange in a GVN.

EPD 100 is the endpoint device. SRV_AP 300 is an access point serverwhich is located in the target destination region. SRV_CNTRL 200 is acentral server accessible by both the EPD and the SRV_AP as well as byother devices which may support a graphic destination mechanism.

Each device EPD 100, SRV_AP 200 and SRV_CNTRL 300 stores informationabout itself in a local information repository in the form of lists,files, database tables and records, and other means. This repositoryalso contains information about peer device relationships, stores logs,plus other relevant operational information. The SRV_CNTRL 200 also hasadditional storage functionality and its role is to provide informationto other devices relevant to them and/or to the peer devices which theymay connect with, to evaluate current conditions and provide centralizedcontrol-like guidance such as the publishing of a server availabilitylist and other functionality. A neutral API mechanism (NAPIM) can sendinfo between devices and the peers which they connect with, and can alsobe used to update the API itself.

The database on the SRV_CNTRL 200 acts as a repository for informationabout itself as well as a centralized repository for other devices.There can be many different SRV-CNTRL 200 servers acting asmultiple-masters in many locations. Each database can store certaininformation including tunnel information, peer information, trafficinformation, cache information, and other information. Security andother aspects are independently managed by each device includingheartbeat functionality, triggered scripts and other mechanisms.

This figure additionally shows the firewall manager D344, D244, D144 onaccess point server (SRV_AP) 300, central control server (SRV_CNTRL)200, and end point device (EPD) 100, respectively. The SRV_AP 300's FWManager D344 communicates with the FW Manager D244 on SRV_CNTRL 200 viapath 15-PA2. Information is available to an EPD's 100 FW Manager D144via path 15-PA1 to receive information from FW Manager D244 on SRV_CNTRL200.

Command and control communications as well as reporting informationconveyance between firewalls SPI 15-SP0-PRO and DPI 15-DP0-PRO is viapaths 15-BA44 and 15-BA42 respectively.

The storage of FW information in databases B344, B244, and D144 onvarious devices allows threats to be known and can also factor intorouting decisions for traffic through a GVN. For example, in the case ofan active attack saturating backbone in one region, this can have anadverse effect on the weighting for traffic via that route, with theeffect of traffic through a less congested pathway to receive routingpriority.

FIG. 16 illustrates device-to-device exchange of information in a GVN.Traffic flow is from the local area network (LAN) 16-002 to firewall(FW) 16-144 device via the path 16-CP144, then to end point device (EPD)16-100 via path 16-CP100. The EPD builds a tunnel TUN 16-0 over the top(OTT) the internet 16-000 to SRV_AP 16-302.

The Data Array 16-144100 containing information about EPD 16-100 isshared to FW 16-144 via paths 16-APSP4 and 16-AP100. The Data Array16-100144 containing information about FW 16-144 is shared to EPD 16-100via paths 16-APSP4 and 16-AP144. In this example, the EPD informationarray is only available via the LAN port and not from the outside via anopen WAN port. It may be available to other trusted devices in the GVNvia TUN 16-0.

The key point is to illustrate an automated method for a device toidentify itself to related devices including information such as itshardware specifications, software version, current operational state,and other relevant information.

FIG. 17 illustrates the integration of a multi-perimeter firewall withother systems in a GVN. Acts of information warfare are alwaysoccurring. Whether they are by nation state, by corporate players,hackers, or other actors, these attacks are relentless and according totrends, the threats are increasing. Utilizing the topology describedherein, there exists the possibility to integrate information about liveattacks which is detected by passive firewalls or other such monitoringmiddle devices on the internet aggregated and reported by securityprovider companies or organizations. Whether the nature of the attack isan intrusion, phishing attack, attempt to steal intellectual property,DDoS attack, or other threat known or unknown, the key point is toprotect one's network.

FIG. 17 shows request/response (REQ/RESP) API loops between variousdevices. These information loops can share information that a cloudfirewall such as CFW-DPI 17-142LB or CFW-SPI 17-144LB learns abouttraffic flowing through it which is reported to SRV_CNTRL 17-200. Theinformation loops can share information about attacks in otherlocalities by passing information from SRV_CNTRL 17-200 to the cloudfirewall such as CFW-DPI 17-142LB or CFW-SPI 17-144LB. Furthermore theinformation stored in the database Db 17-B200 on SRV_CNTRL 17-200 canalso contain heuristic patterns, signatures of known threats, as well asinformation from global internet monitoring feeds to be shared.Visibility for a human administrator can also be made available from ahosted instance on EPD 17-100 via a graphic user interface (GUI) on theClient 17-018 via path 17-GUI-AJAX.

The flexibility of this information exchange topology also allows forperformance monitoring, billing module for cloud-based scalable use offirewall resources, systems administration, and other purposes.

FIG. 20 is similar to FIG. 18 and illustrates the topology of devicesand connectivity for the flow of information to and from an end pointdevice (EPD) 20-100 and the internet 20-002.

The traffic flows from the internet 20-002 to egress ingress point (EIP)20-E2, into access point server (SRV_AP) 20-304, and then via tunnel TUN20-6 to cloud firewall load balancer CFW 20-144LB. This load balancerallocates stateful packet inspection (SPI) firewall resources at FW(SPI) 20-SP0-PRO. This SPI firewall examines the header 20-SP0-Hinformation of packets flowing through it. Threat information detectedby the FW (SPI) 20-SP0-PRO is stored in local database Db 20-BS andshared to central, control server (SRV_CNTRL) 200 via communicationspath 20-APSP4. This information is stored on SRV_CNTRL's database DbB200. Information about threats detected on other SPI firewalls isshared from SRV_CNTRL 200 to FW (SPI) 20-SP0-PRO via communications path20-APSP4.

Traffic that is allowed by CFW 20-144LB to pass flows through TUN 20-4to SRV_AP 20-302. At SRV_20-302, the traffic has two options—it caneither directly flow to EPD via TUN 20-0 with a clone copy of the datastream travelling via TUN 20-2 to the cloud firewall load balancer CFW20-142LB. Or the non-cloned flow can be diverted for filtering andanalysis by the cloud firewall load balancer CFW 20-142LB.

This cloud firewall load balancer CFW 20-142LB allocates deep packetinspection (DPI) firewall resources at FW (DPI) 20-DP0-PRO. This DPIfirewall examines the payload 20-DP0-P information of one or morecombined packets flowing through it. Threat information detected by theFW (DSPI) 20-DP0-PRO is stored in database Db 20-BD and also shared tocentral, control server (SRV_CNTRL) 200 via communications path20-APDP4. This information is stored on SRV_CNTRL's database Db B200.Information about threats detected on other DPI firewalls is shared fromSRV_CNTRL 200 to FW (DPI) 20-DP0-PRO via communications path 20-APDP4.

If allowed, the network traffic then flows from SRV_AP 20-302 to EPD20-100 via TUN 20-0.

SPI and DPI cloud firewall load balancers can learn about systemicthreats, threats find in remote regions, and obtain various otherinformation either via communications with the SRV_CNTRL 200, or in somecases, they may communicate with each other via a direct path such as20-CPSPDP.

FIG. 21 illustrates a multi-perimeter firewall algorithm based on thetopology of FIG. 20 or a similar topology where there are multipleperimeters for various types of firewall operations.

The Db FW threats 21-D122 can be stored on each device and/orcommunicated to a central, control server (SRV_CNTRL) for future accessand use. SPI operations are at one perimeter. DPI operations at eithersame perimeter or another perimeter. SPI and DPI firewalls cancommunicate threats with each other and based on known threats,appropriate steps can be taken.

In this example, traffic starts at 21-000. If threats are detected,threat information is logged and shared and the offending traffic isblackholed at 21-944. Traffic deemed as clear flows out at 21-900.

FIG. 22 illustrates a logical view of the software architecture forfirewall devices such as a cloud firewall CFW 444 and a cloud firewallload balancer device CFW_LB 440 as well as the stacks for relateddevices a central control server (SRV_CNTRL) 200, an access point server(SRV_AP) 300, and an end point device (EPD) 100. As shown, the softwareand hardware can be distributed within the network devices and acrossdifferent circuit boards, processors, network interface cards, storage,and memory.

The software architecture of the devices are very similar to each otherwith the differentiation by role of each device in their operations, andsome differing modules.

The lowest level of each device are the memory (RAM) S106, S206, S306,S406 and processors (CPU) S102, S202, S302, S402 and the networkinterfaces (NIC) S108, S208, S308, S408. All of these are on thehardware level. The operating system (O/S) S110, S210, S310, S410 can bea LINUX system or equivalent system such as Debian or other. Thisdescription of an operating system includes packages and configurationfor routing, hosting, communications and other system level operationssoftware.

The central control server (SRV_CNTRL) 200, access point server (SRV_AP)300, and end point device (EPD) include a system software layer S112,S212, S312 of the Global Virtual Network's (GVN's) operating system.Operating here are custom commands, system modules, managers and otherconstituent parts, as well as other components of the GVN. Each type ofdevice of the GVN may have some or all of these portions of the systemsoftware layer or different portions depending on their role.

Database modules Db 120, 220, 320 and Hosting Modules 122, 222 and 322are configured in this example embodiment for the listening, sending,processing, storage, retrieval and other related foundation leveloperations of the GVN's neutral API mechanism (NAPIM), graphic userinterfaces (GUI) and other server side script hosted sites. Database120, 220. 320 (Db) modules could be MySQL or equivalent such as MariaDband hosting modules 122, 222 and 322 could be Apache and PHP scriptingor other type of hosting languages. Command Line scripts are also usedand can be written in Bash, C, PHP, Pearl, Python or other language.

Billing modules can collaborate and share information such as the amountof data consumed by tunnel traffic to be billed by a consumption model.The accounting module ACC 132 232 332 operates on the EPD 100 and theSRV_AP 300 has a corresponding Billing module. Both can providefinancial information to report screens, payment forms, emailedstatements and other financial data produced by the GVN.

SRV_CNTRL 200 has a Repository Manager 238 which handles billing info,tunnel manager information and other data which can be utilized byvarious devices within the GVN. The Repository Manager 238 also handlesthe coordination of the sharing of peer pair info, credentials and otherinformation to individual devices connecting to other API peers via theneutral API mechanism (NAPIM) of the GVN.

The EPD 100 has an API Module 130, SRV_CNTRL has API Module 230 and theSRV_AP 300 has an API Module 330. For the simplicity of explaining thisexample embodiment only one API module has been expressed per device. Infact, devices may have a combined client and server role depending onits function within the GVN.

A Cache Manager on SRV_CNTRL 200 manages the master index of variouschained caches distributed across many devices of the GVN. TheCompression Engine 136 on the EPD 100 and 336 on SRV_AP 300 manages thecompression and decompression of data both stored on files, in DB tablesor for streaming transport data.

Advanced Smart Routing (ASR) 150 module on EPD 100 handles the routingof traffic from an EPD 100 to the best egress point for destination viaroutes of the GVN.

Remote Fetcher BOT 311 on the SRV_AP 300 is a core component of theGeo-Destination Mechanism (Geo-D).

DNS Manager 254 on SRV_CNTRL 200 manages the master DNS index which canseed DNS Servers on various GVN devices, such as DNS 154 on EPD 100.

A Logger Manager on SRV_CNTRL 200 manages both local logs and logsshared by devices to the Repository via API calls. The Logging Managerin this example embodiment imbues the functionality of recordingoperational events, API actions and transactions and the Logger also hasother roles and processes for various aspects of the GVN operations.

Local Cache 152 on EPD 100 and local Cache 352 on SRV_AP 300 cache datalocally.

GVN Managers 272 operate on SRV_CNTRL 200 to control the operations ofvarious components of the system both on the SRV_CNTRL 200 and otherdevices of the GVN.

Local DNS server and cache 154 on EPD 100 and 354 on SRV_AP 300 allowfor caching of DNS lookups for fast, local retrieval. The DNS 154 and354 can be completely flushed, individual items purged, or timeouts setfor retrieved lookups to be deleted after a certain period of time hastranspired.

On the EPD 100 is a Content Delivery Agent (CDA) 158 which is acomponent of Geo-D. On the SRV_AP 300 is a Content Pulling Agent (CPA)358, also a component of Geo-D. The CPA 358 works with the BOT 311 onSRV_300 to pull content from a distant region using local DNS 354seeding from that Region. The CPA 358 sends fetched content to the CDA158 utilizing tunnels, caches and other improvements of the GVN.

Connectivity Manager (not shown) on EPD 100 and on SRV_AP 300 managesthe tunnels between devices and other device to device communicationspaths. Compression Manager on 215 of SRV_CNTRL 200 manages compressionboth locally and also coordinates with Compression Engines 136 on EPD100, 336 on SRV_AP 300 and on other devices of the GVN. Routing on EPDcoordinates with ASR 150, Geo-D, and other elements to manage trafficrouting.

The structure of the database tables in SDB100, SDB200, and SDB300 areequivalent for device operations while the data for each is specific fordevice types, and each device has identity specific devices. OnSRV_CNTRL 200, the Repository Database SDB202 is where uniqueinformation is stored for all devices and this information can be usedby the Repository Manager 238 to communicate API credentials, tunnelinfo, or other information to a device.

Stored within each device database are identity and API peer info aboutthe device itself and its peer pair partners, transaction lists andqueue data, and other information. There are other uses for thedescribed methods and databases beyond what is described but forsimplicity of illustration, this example only covers a few example corefunctionality elements.

The cloud firewall CFW 444 includes base firewall software S414, as wellas the general rules, DPI, SPI, heuristic scanning, and otherfunctionality S444. The cloud firewall load balancer device CFW_LB 440includes and firewall balancer software S448 which manages traffic flowand resources assignment to cloud firewalls on demand and as needed.

In addition to End point device (EPD) 100, Access point server (SRV_AP)300 and central control server (SRV_CNTRL) 200 third party devices mayalso be utilized as long as they have the ability to communicate plusconfigured credentials and other information to facilitate thiscommunication with other devices. Under each device are some possiblecomponents which could be running within that device's stack, howeversome others may be running concurrently which are not described herein.These components may include FW Connectivity S148 under EPD 100, FWConnectivity S348 under SRV_AP 300, and FW Manager S244 under SRV_CNTRL200. The connectivity and manager modules are for interaction with CFW444 and CFW_LB 440. The manager module conducts ongoing FW analysis andcommunicates with system-wide and geographically diversely located CFWand CFW_LB devices about known threats.

Firewall load balancer CFW_LB 440 to firewall CFW 444 communications canbe by FW Connectivity modules S434 on each device. These connectivitymodules can handle both the data flow channels as well as the channel ofinformation flow about the data flow, the threats detected, and otherinformation.

Device to device communications can be by the Neutral API Mechanism (seeInternational Patent Application No. PCT/IB16/00110) on EPD 100 via APIS130, on SRV_AP 300 via API S330, on SRV_CNTRL 200 via APIS230 and onCFW_LB 440 via API S430.

FIG. 23 illustrates the flow of information from firewalls (FW) tovarious devices in a global virtual network (GVN) via a central controlserver (SRV_CNTRL) 23-200. It also includes the nature of theinformation stored in local devices with respect to the firewallinformation in database (DB) tables such as 23-4100 on DB 23-110,23-4300 on DB 23-300, 23-4200 on 23-210 and also in logs such as 23-4140on FW devices 23-140.

Information is reported from FW devices 23-140 to SRV_CNTRL 23-200 viaAPI request 23-P140 REQ/23-P140 RESP or equivalent device-to-deviceinformation sharing. It can also be report to SRV_CNTRL from individualdevices via paths 23-P102, 23-P302, 23-P502 or other paths from otherdevices.

The SRV_CNTRL 23-200 can broadcast and/or publish FW related informationto devices via paths 23-P100, 23-P300, 23-P500 or other direct paths. FWInformation can also be made available via API call from devices 23-260via request/response paths 23-P260REQ and 23-P260RESP.

Flags can indicate the source of the information such as “detected onthis device”, “detected on another device”, and more, and also theattack origination point such as “LAN based attack to outside”, “WANbased attack”, “attacks from the Wild”, and more.

The stored information can also include signatures, structures known andpredicted via heuristic analysis, IP addresses, code patterns of virusesand/or malware and/or other offending payloads, behavioralcharacteristics of problematic traffic, pattern of propagation, andmore.

The SRV_CNTRL 23-200 can also utilize algorithms to analyze theinformation and also rank the seriousness based on threat longevity,time of first and last detection, scale and scope of attack, and more todetermine the history and any trends. This analysis takes into accountactive threats, past threats, relationships between threats (for examplehow a phishing attack can lead to a compromise that opens a network toother attacks), the current conditions of the internet/network to assignthreat levels and other indicators to measure the intensity of attacks.During relatively quiet times, FW may be more permissive resulting infaster operations. During relatively active times, the FW may be morerestrictive and analytical leading to potentially slower through-put andoperations.

The SRV_CNTRL 23-200 retains FW information in a repository storecataloging threat types, report histories, and logging deviceinteraction including threat information update publishing.

FIG. 24 is a flowchart describing the algorithm used to analyze trafficflowing through a firewall, a firewall load-balancer, and/or through afirewall array. For traffic flowing through, the first step is toevaluate if there are any current, active threats being detected 24-100.This is influenced by the Current Threat State 24-140 which is a rollingindicator of how active the firewall is.

If no threats are detected and the current threat state is normal, thenFW rules are applied to traffic 24-220 and it is allowed through at24-300. It remains in passive threat mode 24-524 and then restarts atthe next Start FW cycle 24-000.

If a threat is detected, traffic flows via path 24-P200 and the threatis checked against list of threat patterns 24-210 via path 24-P210. Ifit is recognized, it is either blackholed or quarantined. Offendingtraffic is logged at 24-240. Once current threats are handled at 24-534,the firewall is set to active threat mode 24-554 and then goes back toStart FW cycle 24-000.

If a threat is not recognized, it is checked using heuristic threatdetection at 24-250. If no threat is detected, if follows via 24-P314 tobe processed as a false positive at 24-314. Mode is upgraded to activethreat mode 24-554 and the next cycle starts at 24-000.

FIG. 25 illustrates the various layers in a system stack to deal withand handle threats. The lowest level of the stack are Memory 25-102,25-202, 25-302, and CPU 25-106, CPU 25-206, CPU 25-306. The system isbuilt up from the lowest level.

The incremental lock down of a device is based on the nature of thethreat and how deep it can go down the stack. For example, theSecure-APP 25-140, 25-240, and 25-340 security layer protect theapplication modules above that layer. These govern the operations ofcertain modules but do not necessary impact the deep logic. Secure-Sys25-124, 25-224, and 25-324 protect the system software layer fordatabase operations, DNS, logging, cache, hosting and otherfunctionality. Secure-O/S 25-114, 25-214, and 25-314 protect theoperating system from threats. Secure-HW 25-104, 25-204, and 25-304protect the physical layer of the hardware system from threats,including driver files, flash-able instruction sets, and other systems.

The lower down the layer locked-down, the less functionality of thesystem.

FIG. 26 illustrates a method for automatically decrypting an encryptedvolume during a boot-up process where system files 26-110 are retrievedfrom HFS File Storage 26-010. At one point in a boot-strap boot upprocess 26-100, the key file 26-210 is retrieved from HFS File Storage26-010. This Key 26-A is used by the Encrypted Volume Unlock Module26-200. Once the encrypted volume is unlocked, it can be used 26-300.

There is an obvious drawback to storing the key to an encrypted volumeon the HFS File Storage Volume 26-010. Because this is susceptible tohackers who gain access to the system to unlock the secure volume usingthe key which is unencrypted. The other threat is to those who take thephysical drive and attempt to either decrypt the volume to stealvaluable client data and/or to reverse engineer the system gainingaccess to software stored in the encrypted volume.

FIG. 27 illustrates how a unique user identification (UUID) can beconsistently computed for a device based on a number of factors specificto that device. Hardware (HW) UUIDs 27-100 such as CPU serial number,CPU model, network interface card (NIC)'s MAC Addresses, and otherfactors are typically unique to each device. Hardware (HW) DMI encoding27-200 can be utilized using burned in DMI values such as serialnumbers, version numbers, or other DMI data. The unique volume ID of ahard disk drive (HDD) or solid state drive (SSD) 27-300 can also beutilized. Certain O/S UUIDs 27-500 can also be utilized which are uniqueto the build of a system. UUID and keys as values in Identity tablestored on local Database 27-600 can also be utilized as part of anidentity for a device.

At the Application level, UUIDs in the form of key files, certificates,and other identifiers 27-800 may be utilized to generate a specific UUIDfor the device itself.

Various device UUIDs can be computed, used, and validated against toensure the veracity of a device's integral operation. The combination ofthe various factors would be hard to near impossible to spoof withoutaccess to the device.

FIG. 28 illustrates the modules of the secure boot mechanism. An endpoint device (EPD) 28-100 contacts a secure boot server (SRV_SB) 28-500and presents a false packet of data via API-2A1-2A5 to which the secureboot server rejects. The SRV_SB then queries the EPD with a set ofchallenges. On successfully passing a series of tests, the Secure BootManager 28-150 on the EPD is allowed to build a secure tunnel TUN28-100500 via the Secure Boot Listener 28-552 on the SRV_SB. The DeviceCredentials 28-138 are presented to SRV-SB to be validated by the SecureBoot Manager 28-550 against values either stored in Database 28-B500 oron the HFS Storage 28-H500.

Only after passing all tests is the key for the encrypted volume on theEPD 28-100 released by the Key and credentials manager 28-536 andconveyed securely to EPD 28-100 via TUN 28-100500. The list of availableSRV_SB servers is available to the EPD via an API query to the central,control server (SRV_CNTRL) 28-200 via Server Availability Mechanism28-222.

FIG. 29 illustrates the details of the back channel mechanism. An endpoint device (EPD) 29-100 receives a list of back channel servers(SRV_BC) which it can connect with via API call API-29A1-29A2 tocentral, control server (SRV_CNTRL) 29-200. The Server Availability29-220 list provides the current available SRV_BCs which the EPD canconnect with. This figure demonstrates three concurrent connections viaTUN 29-100500 to SRV_BC0 29-500, via TUN 29-100502 to SRV_BC2 29-502,and via TUN 29-100506 to SRV_BC6 29-506.

The back channel client 29-510 on the EPD 29-100 makes simultaneousconnections via the back channel managers 29-510, 29-512, and 29-516once security is cleared by BC security 29-540, 29-542, and 29-546. Thedevices can also communicate directly with each other via API calls suchas EPD to SRV_CNTRL via API-29A1-29A2 or SRV_BC0 to SRV_CNTRL viaAPI-29A2-29A50.

Information about peer pairs, credentials, certifications, keys, andother information regarding the building of tunnels between EPDs andSRV_BCs can be conveyed via these API calls to SRV_CNTRL. Furthermore,status messages between known peers which have a healthy relationshipcan be sent directly via APIs such as from EPD 29-100 to SRV_BC2 29-502via API-29A1-29A52.

This example is for one EPD to connect concurrently to many SRV_BC. Thegoal of an active tunnel is to enable an always up path to acommand-line-interface (CLI) log in to the EPD regardless of whether ornot the EPD is discoverable on the open internet and/or network.

FIG. 30 illustrates the connections between many end point devices (EPD)30-100, 30-102, and 30-106 and a back channel server (SRV_BC0) 30-500.While the EPD initiates the connection into a logged-in space on theSRV_BC0 30-500, the instance it is logged into is a System securityisolated instance 30-510 for EPD 30-100, 30-512 for EPD 30-102, and30-516 for EPD 30-106 respectively. Each isolated instance operates likea system jail where the logged in user is only credentialed for a veryfew limited commands restricting their actions, rights, privileges andotherwise their ability to act on the host system.

So from the EPD into the SRV_BC0 30-500, there is very little which canbe done other than to maintain the connection between the two. However,going in the other direction, a Client 30-000 can log into the SRV_BC0and with certain permissions can have the right to access one or more ofthe isolated instances. And from there, can reverse SSH down the tunnelto the login for a remote command line interface CLI 30-110 on EPD30-100, or CLI 30-112 on EPD 30-102, or CLI 30-116 on EPD 30-106. Thisallows the client 30-000 to do administrative tasks, remote hands on,run tests, and conduct other operations within the scope of their loggedin rights. The client can be a human or an automated device.

The advantage of the back channel is to afford access when an EPD isotherwise unreachable. Due to the nature of the tunnels TUN 30-100500,30-102500, and 30-106500, their tolerance to packet loss, jitter, andother factors is much higher than other forms of tunnel and/orcommunications path. Therefore, at times of unstable network, the backchannel provides access to diagnose and remedy issues which otherwisewould be difficult to impossible to address.

FIG. 31 illustrates the writing of encrypted data into selected fieldsin a row of a database using rotating and calculated keys which areunique for every single row.

This process flowchart entails making a connection to database, creatinga row and fetching the corresponding auto-increment integer ROW_IDvalue. Then utilizing an encryption process, the values to be encryptedare subsequently processed using a chain of keys, key adjustors, fieldswithin the row and other factors. The same factors used to encrypt therow of data can be used to decrypt.

TABLE #1 Database with rotating keys and variable data in Encryptedfields # User_ID Key_Adj ENC_A ENC_B Open_A Time_Created Flag Mod_Time658 1 AA S#&*S A(*SD* Open Data 1459164978 1 Mar. 28, 2016 11:36:18 65951 BT DS*W$% (*%SK More Open 1459164978 0 Mar. 28, 2016 11:36:18 660 2DA 3#&SX& #*&S& Open Data 1459164979 1 Mar. 28, 2016 11:36:19 661 1 HC$#*(S(AZ W#E*& Open More 1459164979 2 Mar. 28, 2016 11:36:19 662 36 QP_(V)A($#*A3 A7!D(# Data 1459164980 1 Mar. 28, 2016 11:36:20 663 1 ACD#(sa001 S@!a*9 Readable 1459164988 0 Mar. 28, 2016 11:36:28

Each horizontal row in the table above has two encrypted fields, [ENC_A]and [ENC_B]. The key for each field is rotating based on a number offactors based both on some of the open fields [User_ID], [Key_Adj], and[Time_Created], plus other factors such as base system keys per thefollowing calculation:Key_(calculated)=User_(ID)+Base_(Key)+Key_(Adjustor)+Time_(Created)+Other_(Factors)

Even if the same User_ID inputs the same values for ENC_A and ENC_B atthe exact same second, the values will be different because theauto-increment integer value for Row_ID # (for example for [User_ID]=1at row numbers 658, 661, 663) is a part of the key calculation. The[Key_Adj] or key adjustor field in the example above is a two digitalpha value but could be other data stored in the row. They key point isthat if the SQL of the database is stolen, it is expensive from acomputational and time perspective to crack. The entire code base, SQL,and environment would have to be stolen and replicated to crack thevalues.

FIG. 32 illustrates the decryption of data from a single row using keys,key adjustors, and other factors using a framework to calculated keys.

FIG. 33 illustrates what happens when graphic user interface (GUI)content which is requested by a client 33-000 from an end point device(EPD) 33-100 and the request content is stored within a locked volume33-114. A not found 404 error is thrown and caught by 404 error handler33-144. A jump to simplified content is made at 33-120. This content isstored outside of the locked volume as either files stored on Open HFSfile storage 33-220 or database content from Open DB 33-210 orcombination of both.

If the secure volume is locked, only content outside of the securevolume is available. If however the secure volume is unlocked thensecure content 33-120 from Secure DB 33-210 or files stored on SecureHFS File Storage 33-220 or combination of both can be served.

Javascript scripts within content served can also poll the EPD 33-100 tocheck the state of the secure volume. If it was locked and has beenunlocked, a jump to secure content can be made. And conversely if avolume was unlocked and suddenly becomes locked, then the content canrevert to content outside of the secure volume.

The present disclosure is not to be limited in scope by the specificembodiments described herein. Indeed, other various embodiments of andmodifications to the present disclosure, in addition to those describedherein, will be apparent to those of ordinary skill in the art from theforegoing description and accompanying drawings. Thus, such otherembodiments and modifications are intended to fall within the scope ofthe present disclosure. Further, although the present disclosure hasbeen described herein in the context of at least one particularimplementation in at least one particular environment for at least oneparticular purpose, those of ordinary skill in the art will recognizethat its usefulness is not limited thereto and that the presentdisclosure may be beneficially implemented in any number of environmentsfor any number of purposes. Accordingly, the claims set forth belowshould be construed in view of the full breadth and spirit of thepresent disclosure as described herein.

The invention claimed is:
 1. A multi-perimeter firewall system located in a cloud and forming part of a global virtual network, comprising: an egress ingress point device; a first access point server in communication with the egress ingress point device; a second access point server in communication with the first access point sever; an endpoint device in communication with the second access point server; a first perimeter firewall in communication with the first access point server, wherein the first perimeter firewall performs stateful packet inspection to prevent at least some traffic from passing from the first access point server to the second access point server; and a second perimeter firewall in communication with the second access point server, wherein the second perimeter firewall performs deep packet inspection to prevent at least some traffic from passing from the second access point server to the end point device, wherein at least one of the egress ingress point device, the first access point server, the second access point server, the endpoint device, the first perimeter firewall, or the second perimeter firewall comprises hardware, wherein the deep packet inspection is performed on a cloned copy of traffic that flows through the second perimeter firewall.
 2. The multi-perimeter firewall system according to claim 1, wherein at least one of the access point servers is configured to perform firewall services.
 3. The multi-perimeter firewall system according to claim 1, wherein the first perimeter firewall is in communication with the second perimeter firewall through a communication path.
 4. The multi-perimeter firewall system according to claim 3, wherein the communication path between the first perimeter firewall and the second perimeter firewall is a network path.
 5. The multi-perimeter firewall system according to claim 3, wherein the communication path between the first perimeter firewall and the second perimeter firewall is a network back channel.
 6. The multi-perimeter firewall system according to claim 3, wherein the first perimeter firewall and the second perimeter firewall share threat information including at least one of heuristic patterns, signatures of known threats, known malicious source IP addresses, or attack vectors.
 7. The multi-perimeter firewall system according to claim 6, wherein the first perimeter firewall and the second perimeter firewall share threat information with a central control server.
 8. The multi-perimeter firewall system according to claim 1, wherein the deep packet inspection is performed on flow through traffic.
 9. The multi-perimeter firewall system according to claim 1, wherein at least one of the firewalls includes a cloud firewall load balancer and wherein the cloud firewall load balancer can allocate cloud firewall resources on demand.
 10. The multi-perimeter firewall system according to claim 1, wherein the egress ingress point device receives traffic directly from the Internet.
 11. The multi-perimeter firewall system according to claim 1, wherein the first perimeter firewall is coupled to a multi-honed backbone.
 12. The multi-perimeter firewall system according to claim 1, wherein the at least some traffic prevented from passing from the first access point server to the second access point server includes traffic with recognized malicious headers.
 13. A multi-perimeter firewall system located in a cloud and forming part of a global virtual network, comprising: an egress ingress point device; a first access point server in communication with the egress ingress point device; a second access point server in communication with the first access point sever; an endpoint device in communication with the second access point server; a first perimeter firewall in communication with the first access point server, wherein the first perimeter firewall performs stateful packet inspection to prevent at least some traffic from passing from the first access point server to the second access point server using a first firewall mechanism; and a second perimeter firewall in communication with the second access point server, wherein the second perimeter firewall performs deep packet inspection to prevent at least some traffic from passing from the second access point server to the end point device using a second, different firewall mechanism, wherein at least one of the egress ingress point device, the first access point server, the second access point server, the endpoint device, the first perimeter firewall, or the second perimeter firewall comprises hardware, wherein the deep packet inspection is performed on a cloned copy of traffic that flows through the second perimeter firewall.
 14. The multi-perimeter firewall system according to claim 13, wherein at least one of the access point servers is configured to perform firewall services.
 15. The multi-perimeter firewall system according to claim 13, wherein the first perimeter firewall is in communication with the second perimeter firewall through a communication path.
 16. The multi-perimeter firewall system according to claim 15, wherein the communication path between the first perimeter firewall and the second perimeter firewall is a network path.
 17. The multi-perimeter firewall system according to claim 15, wherein the communication path between the first perimeter firewall and the second perimeter firewall is a network back channel.
 18. The multi-perimeter firewall system according to claim 15, wherein the first perimeter firewall and the second perimeter_firerewall share threat information including at least one of heuristic patterns, signatures of known threats, known malicious source IP addresses, or attack vectors.
 19. The multi-perimeter firewall system according to claim 18, wherein the first perimeter firewall and the second perimeter firewall share threat information with a central control server.
 20. The multi-perimeter firewall system according to claim 13, wherein the deep packet inspection is performed on flow through traffic.
 21. The multi-perimeter firewall system according to claim 13, wherein at least one of the firewalls includes a cloud firewall load balancer and wherein the cloud firewall load balancer can allocate cloud firewall resources on demand.
 22. The multi-perimeter firewall system according to claim 13, wherein the second perimeter firewall is between the endpoint device and the second access point server.
 23. The multi-perimeter firewall system according to claim 13, wherein the first perimeter firewall is between the first access point server and the second access point server.
 24. The multi-perimeter firewall system according to claim 13, wherein the egress ingress point device receives traffic directly from the Internet.
 25. The multi-perimeter firewall system according to claim 13, wherein the first perimeter firewall is coupled to a multi-honed backbone.
 26. The multi-perimeter firewall system according to claim 13, wherein the at least some traffic prevented from passing from the first access point server to the second access point server includes traffic with recognized malicious headers. 